File Transfers for TightVNC

Get a better TightVNC: make a donation ($10 is ok)!

Why File Transfers?

VNC and TightVNC allow to view and control the remote computer, but traditionally do not allow transfering files between the local machine (viewer) and the remote computer (server). So, to copy files, you had to install some stand-alone software such as an FTP server, or SSH/SCP server.

Implementing the file transfer capability in TightVNC will greatly simplify the process of remote networking. For example, if you are using TightVNC for remote user support, you will be able to install software remotely on user's request, upload documentation, etc., thus better serving your clients.

Current Status

Currently, basic file transfer functionality is mostly finished in the Win32 version, and the sources are available in the CVS tree. We plan to make a test release within a week or two.

There is another VNC distribution (Ultr@VNC) supporting file transfers already, but our implementation is different and was developed independently. We made our focus on potentical platform inter-operability, and careful design of new protocol extensions.

Help the Development

Currently we are looking for sponsors, who might be interested to (partially) compensate the time spent on the development of the file transfer functionality. If you would like to have it finished, please make a donation, sending us any amount of your choice. See this page for the information on how to make a donation.

Note that your contribution will result less time to wait for this particular feature to be finished and available in TightVNC.

Contact

Please send your questions and suggestions on our file transfer implementation to the address below:

"Dennis Syrovatsky" <dennis@tightvnc.com>